Skip to main content
Feedback

Boomi DataHub components

The Boomi DataHub system architecture is described in this topic.

The Boomi DataHub system components are as follows:

  • Repositories are virtual runtimes for master data storage in a Boomi Hub Cloud. For example, you could set up a repository to host the following master data domains: Contact, Employee, Partner and Vendor. A repository accepts record updates from contributing sources, matches entities from different sources to one another and propagates source record update requests specifying create, update and delete operations.

  • Integration processes that check for record updates from source systems and source record update requests from the repository and route them accordingly. These processes are also responsible for mapping source record fields to domain fields when updates are sent from sources and vice versa when requests are propagated to sources.

These processes can be built, deployed and managed using only a web browser with Integration. Integration provides the Boomi Master Data Hub connector for this purpose. Alternatively, these processes may be custom-developed using the Boomi DataHub repository REST API.

A Integration process built for this purpose integrates a single domain hosted on a single repository with a single contributing source. If the process connects to a source hosted local, the process must be deployed to an local Runtime. Otherwise, the process can be deployed either local or to a Boomi Runtime cloud.

system architecture diagram

  • A data warehouse, which is an optional component, houses master data for analytics, reporting, visualization, etc. purposes. It does not contribute data to the repository. Master data from the repository is imported into the data warehouse via a manual procedure or a Integration process or other custom-built integration process.

  • The Boomi DataHub service, which is used to model, deploy, and steward master data using only a web browser.